Update name and URL of "ResenseHEX" #7502
Conversation
per1234
added
topic: URL change
|
Hi @per1234. If you intended to submit a library, please check the instructions and update your pull request if necessary: |
github-actions
bot
added
topic: other
per1234
added
topic: URL change
MarkSupp
left a comment
MarkSupp
left a comment
There was a problem hiding this comment.
Hello @per1234 ,
thanks for working on it! Quick question, shouldn't the URL in the registry.txt also be changed, so:
https://github.com/TUDA-MUST/ResenseHEX.git|Contributed|ResenseHEX
|
Hi @MarkSupp. That is exactly what I have done. Please take a look: Line 8732 in 7fa1b79 Note that this pull request consists of two commits; one for each of the distinct maintenance operations being performed:
|
|
Oh sorry, just looked at the first commit and not the overall change, Thank you! |
MatteoPologruto
left a comment
MatteoPologruto
left a comment
There was a problem hiding this comment.
Done:
2026/01/16 15:40:23 Loaded 8823 libraries from DB
Removing Resense HEX
Success!
3 participants
This PR consists of two changes:
https://github.com/TUDA-MUST/Resense-HEX.gittohttps://github.com/TUDA-MUST/ResenseHEX.git(companion to Update name and URL of "Resense HEX" to "ResenseHEX" #7500)Resense HEXtoResenseHEXSince the name change operation on the database is actually a removal followed by automated re-indexing on the next job run, the URL update will occur as a matter of course. For this reason, the only operation required from the backend maintainer is a standard name change procedure.